Skip to content

Update MiniMax-M3 SPEED-Bench AL collector to EAGLE3-GQA head#2290

Draft
qiching wants to merge 3 commits into
mainfrom
albecheng/minimax-m3-eagle3-gqa
Draft

Update MiniMax-M3 SPEED-Bench AL collector to EAGLE3-GQA head#2290
qiching wants to merge 3 commits into
mainfrom
albecheng/minimax-m3-eagle3-gqa

Conversation

@qiching

@qiching qiching commented Jul 20, 2026

Copy link
Copy Markdown
Collaborator

Switch the MiniMax-M3 golden-AL collector from the original MHA head (Inferact/MiniMax-M3-EAGLE3) to the new GQA head
(Inferact/MiniMax-M3-EAGLE3-GQA), which supersedes it (num_key_value_heads=4, 16x smaller draft KV cache). DRAFT_MODEL is now env-overridable so the NVFP4 variant can be collected without editing the script. FLASH_ATTN is retained (works for GQA; backend choice does not affect the measured AL). The golden AL table (golden_al_distribution/minimaxm3_eagle3.yaml) is regenerated by the speedbench-al CI, not hand-edited.

Switch the MiniMax-M3 golden-AL collector from the original MHA head
(Inferact/MiniMax-M3-EAGLE3) to the new GQA head
(Inferact/MiniMax-M3-EAGLE3-GQA), which supersedes it (num_key_value_heads=4,
16x smaller draft KV cache). DRAFT_MODEL is now env-overridable so the
NVFP4 variant can be collected without editing the script. FLASH_ATTN is
retained (works for GQA; backend choice does not affect the measured AL).
The golden AL table (golden_al_distribution/minimaxm3_eagle3.yaml) is
regenerated by the speedbench-al CI, not hand-edited.
@github-actions

Copy link
Copy Markdown
Contributor

Thanks for the contribution! Please reach out to respective companies' CODEOWNER to fill in the latest PR_REVIEW_CHECKLIST.md before pinging core maintainer on Slack for review. In order for the signoff PR check bot to trigger, you must follow the PR_REVIEW_CHECKLIST.md template correctly, including the phrase As a PR reviewer and CODEOWNER, I have reviewed this and have.

For PR verification, add the full-sweep-fail-fast label (strongly recommended) to this PR — the benchmark sweep only runs on labeled PRs. Use full-sweep-enabled only if you need matrix jobs to keep running past a failure.

PR authors are responsible for ensuring that after merging, all GitHub Action jobs fully pass. A lot of the time, failures are just flakes and simply re-running the failed jobs will fix it. See GitHub's docs on re-running failed jobs


感谢你的贡献!请联系相应公司的 CODEOWNER 填写最新的 PR_REVIEW_CHECKLIST.md,然后再在 Slack 上联系核心维护者进行审阅。为了触发 signoff PR 检查机器人,你必须正确遵循 PR_REVIEW_CHECKLIST.md 模板,包括保留英文语句 As a PR reviewer and CODEOWNER, I have reviewed this and have

如需进行 PR 验证,请为此 PR 添加 full-sweep-fail-fast 标签(强烈推荐)— 基准测试 sweep 仅在带有标签的 PR 上运行。仅当需要矩阵任务在失败后继续运行时才使用 full-sweep-enabled

PR 作者有责任确保合并后所有 GitHub Action 任务完全通过。 很多时候失败只是偶发抖动(flake),重新运行失败的任务即可解决。参见 GitHub 关于重新运行失败任务的文档

Albert Cheng (Engrg-Hardware 1) added 2 commits July 20, 2026 15:37
AL is a per-draft acceptance property invariant to concurrency, so batch
prompts to cut wall-clock. Kept at 16 (the max-concurrency the GQA head was
characterized at) to avoid vLLM auto-disabling spec decode under large batches.
AL is a per-draft acceptance property invariant to concurrency, so batch
prompts to cut wall-clock. Kept at 16 (the max-concurrency the GQA head was
characterized at) to avoid vLLM auto-disabling spec decode under large batches.
@xinli-sw

Copy link
Copy Markdown
Collaborator

could you paste AL values ? cc @functionstackx

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants